Domain events for a multi-platform data stream

ABSTRACT

This disclosure relates to methods, non-transitory computer readable media, and systems that relay domain-event objects within an enhanced multi-platform data stream to listen for and react to digital events indicated by the domain-event objects that occur across a wide variety of computing platforms. Specifically, the disclosed systems can receive domain-event objects within the multi-platform data stream. From among the domain-even objects transmitted through the multi-platform data stream, the disclosed systems can identify a domain-event object that is relevant to a digital-analytics platform by identifying domain-event objects that include properties satisfying domain-event-listener rules. Based on an entity identifier and an object event from the relevant domain-event object, the disclosed systems can perform a platform action within the digital-analytics platform (e.g., to react to a change in another platform as indicated by the domain-event object).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/390,385, filed on Jul. 30, 2021. The aforementioned application isencorporated herein by reference in its entirety.

BACKGROUND

In recent years, conventional analytics systems have increasingly drawndata from and operated co-dependently with other computing systems. Inparticular, many conventional analytics systems execute aseparate-data-call computing model to transmit and receive one-offcommunications indicating changes made from other computing systems. Theother computing systems may include sales, coding, messaging, or variousother platforms that operate different software—often with differentsoftware languages and communication protocols than a conventionalanalytics system. To bridge communication barriers between theseparate-data-call computing model of conventional analytics systems andother computing systems (e.g., server-to-server communications), someconventional analytics systems utilize one-off communications that relyon application programming interface (API) calls. Although conventionalanalytics systems often communicate with other computing systems toreflect data changes, they exhibit a number of technical shortcomingsthat hinder efficiently and easily communicating about (and adapting to)cross-system changes and actions.

By transmitting one-off requests to collect information on data oractions that occurred on other computing systems, for example,conventional analytics systems use data requests that lead toinefficient, delayed reactions to changes across multiple computingsystems. In some cases, conventional analytics systems periodicallyrequest individual updates from other computing systems by usingscheduled data requests. Because scheduled data requests occur atpredetermined times, conventional analytics systems often identifychanges in other computing systems (or transmit such changes) at adelayed time rather than when those changes occur in real time. Suchdata requests can accordingly create inefficient cross-system changesand actions. In addition, some conventional analytics systems ofteninefficiently rely on sequential requests (e.g., data-request calls thatoccur in a sequence instead of simultaneously) to create cross-systemchanges and take actions.

Due to the above-mentioned delayed and fragmented communications betweencomputing systems, many conventional analytics systems inefficientlyutilize computing resources. To illustrate, while using data-requestcalls to identify changes in other computing systems, many conventionalanalytics systems transmit data-request calls at separate times. Suchsporadic data-request calls often lead to redundancies in actions thatinefficiently utilize computing resources. For example, a conventionalanalytics system may execute an action for a specific data structurebased on identifying that another computing system changed data. In anexercise in redundancy, an additional outside computing system may alsoindividually identify that the other computing system changed data and,therefore, also take an action for the same specific data structure. Dueto each computing system and the conventional analytics system having toindividually identify data changes across each system, a conventionalanalytics system oftentimes redundantly performs similar actions (tothat of other computing systems) on a same set of data at theinefficient cost of processing power and bandwidth for other tasks.

In addition to inefficient use of computing resources, conventionalanalytics systems often cannot easily communicate with a wide variety ofother computing systems about changes in data or actions. For example,many conventional analytics systems rigidly communicate internal data oraction changes to other internal (or external) computing systems bydetermining which computing systems to send information to regarding thechanges. As many of the computing systems utilize different protocols toreceive such communications, conventional analytics systems oftenutilize a complex and difficult-to-manage set of instructions to keeptrack of which internal (or external) computing system to send theinformation to and also how to send the information. Because only theconventional analytics system determines a relevancy of and sends suchinformation under conventional and rigid protocols, these conventionalanalytics systems often fail to relay information that may have beenimportant to another computing system.

Likewise, because many conventional analytics systems inflexibly utilizea separate-data-call computing model to send scheduled and isolated APIcalls, conventional systems can delay both information updates andcorresponding reactions to the information updates. Because the requestsoften require customized API configurations for each computing systemthat the conventional analytics systems need to check, isolateddate-request calls specific to each of the external (or internal)computing systems often create a seemingly endless list of different APIconfigurations with which to rigidly comply.

Due to such inefficiencies and inflexibilities, many conventionalanalytics systems cannot easily communicate (or identify) changes indata or actions across a wide variety of computing systems to takecohesive and quick reacting actions in light of the wide variety ofactions that are taken on the other computing systems.

SUMMARY

This disclosure describes one or more embodiments of systems,computer-readable media, methods, and computing devices that solve theforegoing problems and provide other benefits. In particular, thedisclosed systems relay domain-event objects within an enhancedmulti-platform data stream to listen for and react to digital eventsthat occur across a wide variety of computing platforms. By relaying andstreaming such domain-event objects, the disclosed systems provide orfeed a multi-platform data stream to which various platforms (orsystems) can listen for domain-event objects and dynamically executechanges, updates, or other platform actions in real (or near-real) time.

For instance, the disclosed systems can receive domain-event objectswithin the multi-platform data stream. From among the domain-evenobjects transmitted through the multi-platform data stream, thedisclosed systems can identify a domain-event object that is relevant toa digital-analytics platform by identifying domain-event objects thatinclude properties satisfying domain-event-listener rules. Based on anentity identifier and an object event from the relevant domain-eventobject, the disclosed systems can perform a platform action within thedigital-analytics platform (e.g., to react to a change in anotherplatform as indicated by the domain-event object). In some embodiments,in response to performing the platform action, the disclosed systems canalso generate and transmit an additional domain-event object for theplatform action into the multi-platform data stream.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingdrawings in which:

FIG. 1 illustrates a block diagram of an environment in which a digitalanalytics system can operate in accordance with one or more embodiments.

FIG. 2 illustrates an overview of a digital analytics system identifyinga domain-event object from a multi-platform data stream and performing aplatform action based on the identified domain-event object inaccordance with one or more embodiments.

FIG. 3 illustrates a schematic diagram of a digital analytics systemgenerating a domain-event object schema in accordance with one or moreembodiments.

FIG. 4 illustrates a graphical user interface for selectabledomain-event-listener conditions and selectable platform-action optionsin accordance with one or more embodiments.

FIG. 5 illustrates a schematic diagram of multiple digital computingsystems respectively identifying domain-event object from amulti-platform data stream and performing platform actions based on therespectively identified domain-event objects in accordance with one ormore embodiments.

FIG. 6 illustrates a schematic diagram of a digital analytics systemperforming platform actions in accordance with one or more embodiments.

FIGS. 7A-7C illustrate graphical user interfaces for selectingdomain-event-listener conditions and platform actions in accordance withone or more embodiments.

FIGS. 8A and 8B illustrate graphical user interfaces for utilizingdomain-event object references in platform action templates inaccordance with one or more embodiments.

FIG. 9 illustrates a schematic diagram of an environment in which adigital analytics system can operate in accordance with one or moreembodiments.

FIG. 10 illustrates a flowchart of a series of acts for identifying adomain-event object from a multi-platform data stream and performing aplatform action based on the identified domain-event object inaccordance with one or more embodiments.

FIG. 11 illustrates a block diagram of a computing device in accordancewith one or more embodiments.

FIG. 12 illustrates a network environment of a digital survey system inaccordance with one or more embodiments.

DETAILED DESCRIPTION

The disclosure describes one or more embodiments of a digital analyticssystem that can generate and relay domain-event objects within anenhanced multi-platform data stream to identify and perform platformactions in response to digital changes or other digital events thatoccur across a wide variety of other computing systems. By generating ordigitally broadcasting domain-event objects within the multi-platformdata stream, the digital analytics system can efficiently communicateevents (e.g., changes or actions) in real (or near-real) time forvarious computing systems (or corresponding platforms) to identify usingdomain-event-listener rules and to perform corresponding actionstriggered by the identified domain-event objects.

For instance, the digital analytics system can receive domain-eventobjects that include entity identifiers and object events within amulti-platform data stream. As explained further below, themulti-platform data stream may include a data stream of internal eventsand/or external events from third-party devices. From among thedomain-event objects in the multi-platform data stream, the digitalanalytics system can identify a domain-event object that satisfiesdomain-event-listener rules corresponding to a digital-analyticsplatform of the digital analytics system. Based on identifying an entityidentifier and an object event from the domain-event object, the digitalanalytics system can perform a platform action within thedigital-analytics platform.

As just mentioned, the digital analytics system can receive domain-eventobjects in a multi-platform data stream. For example, the digitalanalytics system utilizes the multi-platform data stream to communicatedomain-event objects and to listen for domain-event objects acrossmultiple platforms. For example, the digital analytics system canutilize the multi-platform data stream to communicate domain-eventobjects between internal platforms (e.g., a digital analytics platformand other internal platforms) and/or with third-party platforms (e.g.,outside computing platforms or computing services over a network).

When generated or while in a multi-platform data stream, in one or moreembodiments, a domain-event object includes an entity identifier thatindicates an entity and an object event that indicates an event oraction taken in relation to the entity. As part of creating such adomain-event object, the digital analytics system can generate adomain-event object schema that represents the type of entitycorresponding to a specific domain-event object, defines the type ofobject events in relation to that entity, and domain-event-listenerconditions that can be utilized for the specific domain-event object.Indeed, the digital analytics system can include such a domain-eventobject schema within a schema library such that multiple platforms canidentify or transmit domain-event objects within the multi-platform datastream based on the characteristics of the domain-event objects in theschema library.

As noted above, the digital analytics system can utilizedomain-event-listener rules to detect (or identify) domain-event objectsfrom the multi-platform data stream. In some instances, the digitalanalytics system utilizes logic conditions that are flagged when adomain-event object satisfies logic conditions (e.g., satisfies thedomain-event-listener rules). Indeed, in one or more embodiments, thedigital analytics system receives domain-event-listener rules from anadministrator device to associate with a domain-event object and aplatform action. Upon utilizing the domain-event-listener rules toidentify a domain-event object, the digital analytics system can alsoreference content related to the domain-event object by utilizing theentity identifier (or domain-event object identifier) associated withthe domain-event object.

Utilizing the identified domain-event object as a trigger, in one ormore embodiments, the digital analytics system performs a platformaction. More specifically, the digital analytics system identifies thedomain-event object to determine a change or other event that hasoccurred on another computing system (or a platform of the othercomputing system). Then, the digital analytics system performs aplatform action to reflect the change or event that has occurredelsewhere (as indicated by the domain-event object). For instance, thedigital analytics system can perform platform actions such as, but notlimited to, transmitting electronic communications, configuring tickets,triggering platform processes, modifying platform workflows, updating agraphical user interface, uploading a digital reporting interface, ormodifying a platform parameter within the digital-analytics platform ofthe digital analytics system. Furthermore, as mentioned above, uponperforming a platform action, the digital analytics system can alsogenerate a domain-event object to indicate the performed platform actionand transmit the domain-event object into the multi-platform datastream.

To illustrate an example of the digital analytics system utilizingdomain-event objects, in some cases, the digital analytics systemgenerates a set of domain-event-listener rules used to listen fordomain-event objects within a multi-platform data stream that relate tosurvey responses (e.g., an entity). In some instances, an externalcomputing system executing a platform (e.g., a third-party website) cancollect digital survey data from respondent devices and also provide adomain-event objects into the multi-platform data stream whilecollecting the digital survey data. Upon receiving a digital surveyresponse, the external platform can generate and provide a domain-eventobject that indicates that the digital survey response was created.Then, a domain-event listener within the digital analytics system canidentify the domain-event object from the multi-platform datastream—because the domain-event object relates to a specific surveyresponse (e.g., low-customer-satisfaction score) and satisfies the setof domain-event-listener rules. Indeed, the digital analytics system cantrigger a platform action to analyze the digital survey responseindicated within the domain-event object (from the external platform)upon identifying the domain-event object within the multi-platformstream.

As suggested above, the disclosed digital analytics system overcomesseveral technical deficiencies of conventional analytics systems thatexecute separate-data-call computing models. By utilizing domain-eventobjects and an enhanced multi-platform data stream, to the discloseddigital analytics system flexibly and efficiently communicates across awide variety of computing systems (or platforms associated with thesystems) and dynamically reacts to digital events across a wide varietyof computing systems. Indeed, the digital analytics system can utilizedomain-event objects to communicate with other computing systems to takedynamic actions that are coordinated with a wide variety of othercomputing systems (e.g., as self-organizing systems that enable richintegration between systems). Unlike the separate-data-call computingmodels of many conventional analytics systems, the digital analyticssystem's democratized-domain-event streaming model utilizes domain-eventobjects to decrease communication errors, increase communication speed(e.g., in real or near-real time), and increase automation of tasks(e.g., user interface updates, updating datasets, initiating triggersfor automated tasks as described herein) across a wider variety ofinternal platforms and/or external computing systems.

Indeed, the digital analytics system improves the flexibility ofidentifying changes in a wide variety of computing systems in real (ornear-real) time by utilizing domain-event objects and the multi-platformdata stream. In many cases, the digital analytics system can communicatewith other computing systems using the domain-event objects in themulti-platform data stream without having to check for a compatible APIto request such information at each individual computing system. Byrelaying the domain-event objects in the multi-platform data stream,system-to-system communication is democratized such that the digitalanalytics system can communicate to a wider variety of computing systemswithout having to individually manage API protocols for each of thesystems as done in many conventional analytics systems that executeseparate-data-call computing models.

To illustrate, in contrast to conventional analytics systems thatexecute separate-data-call computing models to periodically look forchanges in other computing systems by making isolated and specificrequest calls for information, the digital analytics system can listenfor events of other computing systems in real (or near-real) timewithout having to make isolated calls and without having to determinewhich other computing systems may have relevant information for thedigital analytics system. In particular, the digital analytics systemcan configure domain-event object-listener rules for specific eventsthat are relevant to the digital analytics system. Then, the digitalanalytics system can identify domain-event objects that indicate thespecific digital events indicated by the domain-event objects as theyoccur on a wide variety of computing systems.

Moreover, by generating or relaying domain-event objects in the enhancedmulti-platform data stream, the disclosed digital analytics system alsoimproves the flexibility of automated system-to-system interactions. Inparticular, the domain-event objects and the multi-platform data streamenables the digital analytics system to listen for domain-event objectsof a wide variety of computing systems and dynamically react to theseother systems with reduced human interference. The digital analyticssystem can flexibly perform actions in response to other computingsystems in real (or near-real) time by utilizing an algorithm and acomputer structure that enables the creation of domain-event objects bythe wide variety of computing systems. In other words, the enhancedmulti-platform data stream enables the digital analytics system toidentify domain-event objects and automatically perform platform actionsbased on identified domain-event objects.

Furthermore, unlike many conventional analytics systems thatindividually determine the relevant information to provide to multipleother computing systems, the digital analytics system can easilycommunicate to a wide variety of systems through domain-event objectsand the multi-platform data stream with a reduced number of internaldeterminations. For example, the digital analytics system easilytransmits domain-event objects for actions performed by the digitalanalytics system to the multi-platform data stream without having todetermine the relevancy of the information for a number of individualcomputing systems. Rather, upon transmitting the domain-event objects tothe multi-platform data stream, the digital analytics system facilitatesa wide variety of computing systems to listen for events that arerelevant to those systems and perform actions based on the identifieddomain-event objects.

In addition to flexibility, in some embodiments, the digital analyticssystem utilizes domain-event objects and the multi-platform data streamto improve the efficiency of system-to-system communications andmulti-platform aware actions. To illustrate, by having access todomain-event objects from multiple platforms that indicate digitalevents that have occurred in relation to those platforms, the digitalanalytics system (and various other computing systems) can react todigital events from a wide variety of computing systems by performingplatform actions in real time. In contrast to the separate-data-callcomputing models of conventional analytics systems that periodicallyfield isolated data-request calls that can delay updates, the digitalanalytics system can listen in real (or near-real) time for domain-eventobjects created by other computing systems to identify digital changesor other events that have occurred at those computing systems via theenhanced multi-platform data stream.

In addition to faster and more efficient updates, the digital analyticssystem more efficiently broadcasts digital events in a multi-platformdata stream in contrast to conventional API calls. Unlike conventionalanalytics systems that execute separate-data-call computing models thatindividually make isolated request calls to multiple other computingsystems, the digital analytics system utilizes an enhancedmulti-platform data stream that shares domain-event objects from each ofa wide variety of computing systems (and/or internal platforms of thedigital analytics system) such that each computing system can listen forand react to digital events indicated by the domain-event objects inreal time. The multi-platform design of the multi-platform data streamaccordingly enables the digital analytics system to reduce the number ofoverlapping (or redundant) platform actions to efficiently utilize itscomputing resources and processing bandwidth. To illustrate, unlikeconventional analytics systems that may receive outdated informationfrom other computing systems and perform actions in relation toparticular actions that may have already been performed by anothersystem, the digital analytics system receives and relays such actions inreal time by listening for domain-event objects through the enhancedmulti-platform data stream. Accordingly, the digital analytics systemidentifies such actions from domain-event objects and reduces the numberof redundant tasks (or actions) performed by the digital-analyticsplatform of the digital analytics system. Additionally, unlikeconventional API calls, in some cases, the digital analytics systemutilizes a domain-event object that standardizes the metadata payload ofcommunications to efficiently democratize communications betweensystems.

In addition to multi-platform efficiency, the digital analytics systemmore efficiently utilizes a computer and/or data structure throughgenerating and utilizing domain-event objects and the enhancedmulti-platform data stream. Indeed, by utilizing domain-event objectsand the enhanced multi-platform data stream to change the computer modelof how a wide variety of computing systems (or internal platforms of thedigital analytics system) dynamically react to one another minimizes theimpacts these computing systems (and the utilized network) have oncommunication networks. As mentioned above, the domain-event objects andthe enhanced multi-platform data stream enables the digital analyticssystem to efficiently utilize its bandwidth to perform other actions andalso reduces the amount of computing resources utilized on redundanttasks, react quickly to changes or other digital events across a widevariety of computing systems, and also improves automation by enablingdynamic and reactive functionalities across multiple systems (orplatforms of the systems).

As illustrated by the foregoing discussion, the present disclosureutilizes a variety of terms to describe features and advantages of thedigital analytics system. For example, as used herein, the term“domain-event object” refers to a data object that indicates a result oraction in relation to an object. In particular, a domain-event objectincludes a data packet comprising (i) an entity identifier thatindicates a particular entity and (ii) an object event that indicatesthe result or action in relation to the particular entity. For example,a domain-event object can include an entity identifier for an entity(e.g., contact, form, response, list member), an object event (e.g.,created, published, assigned, sent), and other attributes (e.g.,creation time, language, source, transmission time, originatingplatform). Additionally, in some embodiments, a domain-event object canalso include attributes such as, but not limited to, sentiment values(e.g., numerical representations and/or text descriptions of asentiment), experience data (e.g., data representing a user's ororganization's impression of, description of, rating for, or reaction toanother entity or a service), and/or data derived from machine learningmodels implemented by the digital analytics system (or anotherthird-party system).

In some embodiments, a domain-event object corresponds to a domain-eventschema. For example, as used herein, the term “domain-event schema”refers to an information structure for a domain-event object thatdefines the types of information, actions, and functions that areassociated with the domain-event object. For instance, a domain-eventschema can include definitions for, but is not limited to, the type ofattributes to include, naming conventions, event types, entityidentifier formats, and event-listener conditions for a domain-eventobject.

In addition, as used herein, the term “schema library” includes acollection of domain-event objects and corresponding domain-event objectschemas. For instance, the digital analytics system can referencedomain-event object schemas from a schema library to identifydefinitions for a domain-event object and domain-event-listener rulesfor the domain-event object when initializing and configuring a digitallistener to listen for a specific domain-event object within amulti-platform data stream. When the specific domain-event object isidentified, as indicated above, the disclosed digital analytics systemcan perform a corresponding platform action.

In addition, as used herein, the term “entity identifier” refers to avalue, an alphanumeric, string, hash, or other digital indicator thatreferences an entity (e.g., a specific entity). For example, entityidentifier can include a pointer address to a particular entity. Inaddition, the entity identifier can also indicate an entity type. Toillustrate, in one or more embodiments, an entity identifier for aparticular entity (e.g., a survey response) can include a value of“dap.events.surveyresponse.1234” for a survey response from adomain-event object of a digital analytics platform with anidentification number of 1234 for the specific survey response entity.

Furthermore, as used herein, the term “entity” refers to a data objectthat includes particular rules, data, and/or functions within acomputing system. In some cases, an entity represents a data objectdefined by both an identity and a thread of continuity (e.g., creation,transmission, deletion times). The entity can include a reference to aset of functions and other information that defines the entity'sidentity. For example, an entity can include, but is not limited to, acontact, a form, a ticket, a response, a distribution, a surveyinvitation, a list member, a segment member, a survey response, adigital survey, an electronic communication, a sentiment, or acalculated trend value.

In some embodiments, a domain-event object can include an entityidentifier that points to a root entity. In particular, the digitalanalytics system can identify a root entity from a domain-event objectthat branches to one or more entities. By doing so, the digitalanalytics system can utilize the entity identifier in a domain-eventobject to reference and retrieve a root entity and various otherentities that branch (e.g., hierarchical relationships, cascadingrelationships) from the root entity. For example, the digital analyticssystem can identify a digital survey entity as a root entity thatreferences branching entities (e.g., aggregate entities) such as, butnot limited to, survey response entities, survey question entities, andanswer choice entities. In addition, the digital analytics system canidentify an entity in a domain-event object that can be a composition ofother entities. For example, in some embodiments, a list entity within adomain-event object do not include list members (e.g., the list entitybeing a composite entity). In some instances, the digital analyticssystem can retrieve the entities (e.g., the list members) of thecomposite entity (e.g., the list entity) by traversing a databaseutilizing the composite entity as a reference. In some embodiments, adomain-event object includes various types of entities (e.g., a rootentity, composite entity, a standalone entity, an entity that is abranched entity from a root entity or composite entity).

As used herein, the term “object event” refers to an indication of aresult, action, status, or fact associated with a domain-event object inrelation to an entity. For example, an object event can represent a codeor text descriptor that describes a result, action, status, or fact inrelation to an entity. As an example, an object event can include, butis not limited to, a text descriptor that indicates a creation of, anassignment of, a transmission of, a modification to, an interactionwith, a publication of, an update of, a sharing of, a subscription to,an unsubscription to, a scheduling of, a calculation of, a rejection of,a proposal of, or a review (or in-review status) of a digital entity.For instance, an object event can include a descriptor that indicateswhether a digital survey has been activated or deactivated for a digitalsurvey entity (referenced within a domain-event object).

In one or more embodiments, the digital analytics system monitors suchdomain-event objects and corresponding entities and objects events inthe context of a platform for experience management of user interactionswith an organization. For example, an entity and object event canidentify or represent a survey response that is submitted by a userdevice through an application or a website monitored or tracked by aplatform for experience management for a particular organization (e.g.,third-party application or organization's website). Moreover, the entityand object event can also identify or represent a user interaction(e.g., a view, a selection) of a user device within an application orwebsite monitored or tracked by a platform for experience management fora particular organization. In some cases, the entity and object eventcan also include interactions of users within an organization (e.g.,employee interactions with the organization, employee interactions withother employees, employee interactions with users of an organizationalwebsite and/or application). As explained further below, in some cases,such object events can correspond to a domain-event object that triggersa platform action executed by or within a platform for experiencemanagement.

Furthermore, as used herein, the term “digital message platform” refersto a storage and/or transmission component that facilitates the storageand/or transfer of domain-event objects that is accessible by multipleplatforms (and/or computing systems that implement the multipleplatforms) as a multi-platform data stream. For instance, a digitalmessage platform can include a memory component that enables storage andaccess to one or more domain-event objects to create a multi-platformdata stream of domain-event objects. In some cases, the digitalanalytics system utilizes a digital message platform that facilitates amulti-platform data stream such as, but not limited to, apublisher-subscriber platform (e.g., Apache Kafka) and/or anotherstreaming platform implementation.

As mentioned above, a digital message platform can facilitate amulti-platform data stream of domain-event objects. In one or moreembodiments, the term “multi-platform data stream” refers to a stream ofinformation (e.g., data packets of domain-event objects) accessible bymultiple platforms (e.g., through a digital message platform). Forexample, a multi-platform data stream of a digital message platform canbe accessed by multiple computing systems (or computing devices) toidentify or transmit domain-event objects between the multiple computingsystems (or associated platforms). Indeed, the digital analytics systemcan utilize a multi-platform data stream within a digital messageplatform that is implemented using any communication platforms andtechnologies suitable for transporting data and/or communicationsignals, including the examples described below with reference to FIGS.11 and 12 .

As used herein, the term “domain-event-listener rule” refers to a logicrule or condition that defines a domain-event object, an entityidentifier for a domain-event object, an object event for a domain-eventobject, or other attribute of a domain-event object targeted foridentification. For instance, a domain-event-listener rule can includeBoolean logic to compare attributes of a domain-event object toconditions for those attributes. In particular, a domain-event-listenerrule can include logic conditions such as, but not limited to, a checkfor a type of digital entity, a check for a digital-entity-creationtime, a check for an object-event-occurrence time, or a check for anobject-event type. As an example, a domain-event-listener rule caninclude a condition to check if a type of digital entity is a “surveyresponse” and to check if an object-event type is “created.” Indeed, thedigital analytics system can identify (or listen for) domain-eventobjects within a multi-platform data stream that satisfy theabove-mentioned domain-event-listener rule by identifying a domain-eventobject that includes a survey response as the digital entity type and“created” as the object event (e.g., returning a true flag for the logiccondition).

As used herein, the term “platform action” refers to an act,modification, process, or operation in relation to data corresponding toa particular platform of a system. In particular, a platform action caninclude a variety of actions, modifications, processes, or operationsthat modify or create the state, location, accessibility, display, orvalue of data or data objects. For example, a platform action caninclude, but is not limited to, a transmission of an electroniccommunication, a configuration of a ticket, a triggering of a platformprocess, a modification of a platform workflow, an update of a graphicaluser interface (e.g., digital reporting interface), a modification of aplatform parameter, or creation of a digital calendar event.

Relatedly, the term “platform” refers to a technological environment forwhich software components and applications are developed and withinwhich computing devices operate software components and applications.For example, a platform may include server devices that execute aspecific software language or machine language code and also run a typeof software or suite of compatible software applications. A platform maylikewise use a data model that is specific to the platform and thatspecifies data formats (e.g., entities, object events) for storing,sending, and receiving data. Accordingly, one platform's data model maydiffer from and be incompatible with another platform's data model.

In addition, the term “digital analytics platform” refers to atechnological environment in which software components and applicationsoperate to analyze and determine conclusions concerning data. Forexample, a digital analytics platform can include software componentsand applications to generate, analyze, and present conclusions orsummaries of digital surveys. The digital analytics platform can alsoinclude software components and applications to receive, analyze, and/orcommunicate various components of digital surveys (e.g., surveyresponses, digital survey reports, digital survey links) via electroniccommunication components, machine learning components, digital surveymanagement components. In some cases, the digital analytics platform caninclude a software component and/or application that performs a specificfunction (e.g., analyzing digital surveys) within an overarchingcomputing system (e.g., the digital analytics system) that receives,analyzes, and/or communicates various components of digital surveys.

Turning now to the figures, FIG. 1 illustrates a block diagram of asystem 100 (or environment) in which a digital analytics system 104operates in accordance with one or more embodiments. As illustrated inFIG. 1 , the system 100 includes server device(s) 102, an administratordevice 112, respondent devices 110 a-110 n, and a third-party platform114. Furthermore, as shown in FIG. 1 , the server device(s) 102 includethe digital analytics system 104. In addition, the digital analyticssystem 104 includes a domain event listener 116, a digital messageplatform 118, and a multi-platform data stream 120.

Generally, the administrator device 112 and respondent devices 110 a-110n may be any one of various types of client devices. For example, theadministrator device 112 and respondent devices 110 a-110 n may bemobile devices (e.g., a smart phone, tablet), laptops, desktops, or anyother type of computing devices, such as those described below withreference to FIGS. 11 and 12 . Additionally, the server device(s) 102may include one or more computing devices, including those explainedbelow with reference to FIGS. 11 and 12 . The server device(s) 102, theadministrator device 112, the third-party platform 114, and therespondent devices 110 a-110 n may communicate using any communicationplatforms and technologies suitable for transporting data and/orcommunication signals, including the examples described below withreference to FIGS. 11 and 12 .

In one or more embodiments, the administrator device 112 and therespondent devices 110 a-110 n are associated with a type of user. Anadministrator is associated with the administrator device 112 and usesthe administrator device 112 to manage the creation and configuration ofdomain-event objects (and, in some cases, the creation and distributionof a digital surveys). Furthermore, respondents are respectivelyassociated with the respondent devices 110 a-110 n and provide data(e.g., digital survey responses and website/application interactiondata).

To access the functionalities of the digital analytics system 104, incertain embodiments, an administrator interacts with an administratordevice application on the administrator device 112. Similarly, to accessother functions of the digital analytics system 104, in someimplementations, respondents interact with respondent deviceapplications, respectively, on the respondent devices 110 a-110 n. Insome embodiments, one or both of the administrator device applicationand the respondent device applications comprise web browsers, applets,or other software applications (e.g., native applications or webapplications) available to the administrator device 112 or therespondent devices 110 a-110 n, respectively. Additionally, in someinstances, the digital analytics system 104 provides data packetsincluding instructions that, when executed by the administrator device112 or the respondent devices 110 a-110 n, create or otherwise integratethe administrator device application or the respondent deviceapplications within an application or webpage for the administratordevice 112 or the respondent devices 110 a-110 n, respectively.

As an overview, the server device(s) 102 provide the administratordevice 112 access to the digital analytics system 104 by way of thenetwork 108. In one or more embodiments, by accessing the digitalanalytics system 104, the server device(s) 102 provide one or more userinterfaces and/or data to the administrator device 112 to enable anadministrator to configure domain-event objects, domain-event-listenerrules, and/or platform actions associated with the domain-event-listenerrules. For example, the digital analytics system 104 can include awebsite (e.g., one or more webpages) or utilize an administrator deviceapplication on the administrator device 112 to enable the administratorto create domain-event objects, domain-event-listener rules, and/orplatform actions associated with the domain-event-listener rules. Inaddition, the digital analytics system 104 can also provide the websiteor the administrator device application on the administrator device 112to enable the administrator to create digital surveys or other digitalcontent for distribution to the respondent devices 110 a-110 n,configure digital survey data, access digital survey data, or accessother analytics tools and/or functions corresponding to the digitalanalytics system 104 (e.g., via graphical user interfaces).

Furthermore, in some embodiments, the respondent devices 110 a-110 ninteract with the administrator device 112, the digital analytics system104, or the third-party platform 114. From the interactions, theadministrator device 112 (or the third-party platform 114 or the digitalanalytics system 104) identifies data (e.g., digital survey data and/orother interactions with websites or applications) from the respondentdevices 110 a-110 n. Indeed, the digital analytics system 104 canutilize the data from the respondent devices 110 a-110 n to generatedigital survey statistics, reports, and/or other analytics data. Suchdigital survey statistics, reports, and/or other analytics data can beprovided to the administrator device 112 (within graphical userinterfaces as analytics tools) by the digital analytics system 104.

During the actions taken by the digital analytics system 104 and/or theactions taken by either the administrator device 112 and/or therespondent devices 110 a-110 n, the digital analytics system 104generates domain-event objects for the actions and data modifications.Additionally, in reference to FIG. 1 , the digital analytics system 104places these domain-event objects into the digital message platform 118of the digital analytics system. Indeed, the digital analytics system104 utilizes the digital message platform 118 to share domain-eventobjects across different platforms that internally operate within thedigital analytics platform.

For example, the digital analytics system 104 can include a variety ofplatforms (e.g., a digital analysis platform, an electroniccommunication platform, a graphical user interface platform, a billingplatform) that can each utilize domain-event listeners that listen fordomain-event objects. Indeed, a platform from within the digitalanalytics system 104 can generate domain-event objects for an actiontaken by the particular platform. Then, in one or more embodiments, thedomain-event listeners of the other platforms can identify the generateddomain-event object and take one or more platform actions that reflectthe generated domain-event object (e.g., if the domain-event objectsatisfies a set of domain-event-listener rules).

Furthermore, in one or more embodiments, the digital analytics system104 also feeds or places domain-event objects into the multi-platformdata stream 120. Indeed, the digital analytics system 104 can utilizethe multi-platform data stream 120 to transmit (or share) domain-eventobjects between internal platforms of the digital analytics system 104(e.g., through the digital message platform) and also to third-partyplatforms via the network 108. For example, the digital analytics system104 (via one or more platforms) can introduce domain-event objectswithin the multi-platform data stream 120. Then, the third-partyplatforms can identify the domain-event objects within themulti-platform data stream 120 and perform platform actions based on thedomain-event objects.

In addition, the digital analytics system 104 can receive domain-eventobjects within the multi-platform data stream 120 from third-partyplatforms. Once received in the multi-platform data stream 120, avariety of platforms within the digital analytics system 104 can receivethe domain-event objects from the multi-platform data stream 120 (e.g.,via the digital message platform 118). Indeed, the various platforms ofthe digital analytics system 104 can utilize domain-event-listener ruleswithin the domain event listener 116 (e.g., specific domain-eventlisteners to the platforms) to identify relevant domain-event objectsthat satisfy the domain-event-listener rules. Subsequently, the one ormore platforms (or the digital analytics system 104) can perform one ormore platform actions based on the identified domain-event objects (inaccordance with one or more embodiments).

In some embodiments, the server device(s) 102, the administrator device112, the respondent device(s) 110 a-110 n, and the third-party platform114 can communicate over the network 108. For instance, the network 108enables communication between components of the system 100. In one ormore embodiments, the network 108 includes a suitable network and maycommunicate using any communication platforms and technologies suitablefor transporting data and/or communication signals, examples of whichare described with reference to FIGS. 11 and 12 . Furthermore, althoughFIG. 1 illustrates the server device(s) 102, the administrator device112, the respondent device(s) 110 a-110 n, and the third-party platform114 communicating via the network 108, in certain implementations, thevarious components of the system 100 communicate and/or interact viaother methods (e.g., the server device(s) 102 and the administratordevice 112 communicating directly).

Furthermore, although FIG. 1 illustrates the digital analytics system104 being implemented by a particular component and/or device (e.g.,server device(s) 102) within the system 100, the digital analyticssystem 104 can be implemented, in whole or in part, by other computingdevices and/or components in the system 100. For example, the digitalanalytics system 104 can be implemented in whole, or in part, by theadministrator device 112. In particular, the digital analytics system104 can operate on the administrator device 112 to generate domain-eventobjects and listen for domain-event objects.

As mentioned above, the digital analytics system 104 utilizesdomain-event objects within a multi-platform data stream to communicateand automatically react to digital events occurring across a widevariety of platforms. FIG. 2 provides a brief overview of one embodimentof the digital analytics system 104 identifying a domain-event objectfrom a multi-platform data stream and performing a platform action basedon the identified domain-event object. More specifically, FIG. 2illustrates the digital analytics system 104 receiving domain-eventobjects within a multi-platform data stream and utilizingdomain-event-listener rules to identify a given domain-event object fromthe multi-platform data stream. Furthermore, FIG. 2 also illustrates thedigital analytics system 104 performing a platform action based on theidentified domain-event object that satisfies the domain-event-listenerrules.

As shown in FIG. 2 , the digital analytics system 104 receivesdomain-event objects within a multi-platform data stream in an act 202.As illustrated in the act 202 of FIG. 2 , the digital analytics system104 utilizes a multi-platform data stream to receive domain-eventobjects (e.g., domain event objects 1-N) from multiple platforms (e.g.,server devices of internal platforms of the digital analytics system 104and also third-party platforms). The domain-event objects correspond todomain-event object schemas from a schema library such that the digitalanalytics system 104 (and other computing systems) can recognize thedomain-event objects within the multi-platform data stream. Indeed, thedigital analytics system 104 generating domain-event objects and adomain-event object schema are described in greater detail below (e.g.,in relation to FIG. 3 ).

Furthermore, as shown in FIG. 2 in act 204, the digital analytics system104 identifies a domain-event object that satisfiesdomain-event-listener rules corresponding to a digital-analyticsplatform. Indeed, the digital analytics system 104 checks conditions ofthe domain-event-listener rules to attributes of the domain-eventobjects within the multi-platform data stream to identify domain-eventobjects that satisfy the domain-event-listener rules. The domain-eventobjects that satisfy the domain-event-listener rules are selected by thedigital analytics system 104. Indeed, as shown in the act 204 of FIG. 2, the identified domain-event object includes an entity identifier andan object event. The digital analytics system 104 identifiesdomain-event object utilizing domain-event-listener rules and generatesdomain-event-listener rules are described in greater detail below (e.g.,in relation to FIGS. 4, 5, and 7-8 ).

Additionally, as shown in act 206 of FIG. 2 , the digital analyticssystem 104 performs a platform action based on the identifieddomain-event object. In particular, the digital analytics system 104 canperform a platform action in response to an object event identifiedwithin a domain-event object. For example, as shown in FIG. 2 , thedigital analytics system 104 performs platform actions, such astransmitting an electronic communication, triggering a platform process,modifying a workflow, updating a digital reporting interface, modifyingparameters, and/or configuring a ticket. Indeed, this disclosuredescribes platform actions and the digital analytics system 104performing platform actions based on a domain-event object in greaterdetail below (e.g., in relation to FIGS. 4, 5, and 6 ).

As mentioned above, the digital analytics system 104 can identify adomain-event object generated by an administrator device. In particular,an administrator device can generate or select settings for adomain-event object schema that includes a structure for a domain-eventobject. The domain-event object schema can be included in a schemalibrary such that the digital analytics system 104 (and/or othercomputing systems) may generate domain-event objects or listen fordomain-event objects as defined by the domain-event object schema.

For instance, FIG. 3 illustrates the administrator device 112 generatinga domain-event object schema 302 for a schema library 304. Inparticular, as shown in FIG. 3 , the administrator device 112 providesselections for a domain-event object 306 that includes one or moreentity identifiers 308 and object-event types 310. In addition, theadministrator device 112 also provides domain-event-listener conditions312 for the domain-event object 306. As shown in FIG. 3 , the one ormore entity identifiers 308, the object-event types 310, and thedomain-event-listener conditions 312 form the domain-event object schema302.

Additionally, as shown in FIG. 3 , the digital analytics system 104includes the domain-event object schema 302 from the administratordevice 112 into the schema library 304. Indeed, as shown in FIG. 3 , theschema library 304 includes multiple domain event object schemas (e.g.,domain event object schemas 1-N). In one or more embodiments, thedigital analytics system 104 (and/or other computing systems) can accessthe domain event object schemas within the schema library 304 todetermine domain-event-listener rules to utilize to listen for specificdomain-event objects in a multi-platform data stream. In someembodiments, the domain-event-object schemas in the schema library caninclude domain-event-object schemas that are generated by administratordevices operating within the digital analytics system 104 and/or variouscombinations of other third-party platforms.

In some instances, the administrator device 112 can provide entityidentifier information to define entity identifiers for adomain-event-object schema. Particularly, the administrator device 112can provide (or indicate) a type of entity for the domain-event objectschema. For example, the type of entity can include an indication of aparticular entity that is associated with the domain-event objectschema. In some instances, the entity type is a defined object withinthe digital analytics system 104 (or other computing systems) thatincludes pre-existing functionalities and/or data structures. Toillustrate, the digital analytics system 104 can generate adomain-event-object schema for survey responses by including a surveyresponse object as an entity type. Then, in one or more instances, thedomain-event objects based on the domain-event-object schema for asurvey response include a reference to a survey response and the one ormore available functionalities and/or data structures of a surveyresponse object.

Additionally, the digital analytics system 104 can generate an entityidentifier for a specific entity (or entity type) selected by theadministrator device 112. For example, the digital analytics system 104can generate an entity identifier that indicates an entity type and alsopoints to a specific entity. In some cases, the digital analytics system104 can utilize an internal identification of the entity as the entityidentifier (e.g., an identification string or number that points to theentity within the digital analytics system 104 or one or more platformsoperating within the digital analytics system 104). In one or moreembodiments, the digital analytics system 104 (via a variety ofplatforms) utilize the entity identifier associated with thedomain-event object to reference the entity corresponding to thedomain-event object.

Moreover, the digital analytics system 104 can also generateobject-event types for a domain-event object schema. In particular, thedigital analytics system 104 can receive selections (or definitions) forobject-event types for a domain-event object schema. Then, the digitalanalytics system 104 can correspond the object-event types within thedomain-event object schema in relation to a received entity type. In oneor more embodiments, the received object-event types can define thetypes of events (e.g., actions or states) that can occur in relation tothe entity corresponding to the domain-event object. As such, thedigital analytics system 104 can perform an action in relation to anentity and generate domain-event objects for the entity specified in thedomain-event object schema with a given object event that represents theperformed action.

Furthermore, the digital analytics system 104 can include (or generate)domain-event-listener conditions for a domain-event object schema. Toillustrate, the digital analytics system 104 can receive selections (orconfigurations) of logic operations as domain-event-listener conditionsfor the domain-event object schema. In particular, the digital analyticssystem 104 can receive a various combinations of logic operations thatindicate a logic comparison between a selected entity and object eventassociated with the domain-event object schema. As an example, theadministrator device 112 can provide a specific combination of logicthat checks whether an entity experiences a combination of object events(e.g., a survey response is created and stored, a survey response iscreated or stored, a survey response is created and not stored). In someinstances, the domain-event object schema can include such combinationsof logic as default domain-event-listener conditions that can beselected while configuring domain-event-listener rules.

In some cases, the digital analytics system 104 can also includedomain-event-listener conditions in a domain-event object schema thatdefine various logic conditions that can be utilized for thedomain-event object. For example, the digital analytics system 104 caninclude domain-event-listener conditions, such as, but not limited to, a“greater than” condition, a “less than” condition, an “equal to”condition, or a “contains” condition.

In addition, the digital analytics system 104 can also include (orgenerate) other attribute descriptor types for a domain-event objectschema. For example, the attribute descriptor types can include optionsto include various attribute descriptors in relation to an entity,object event, or the domain-event object. In some cases, the digitalanalytics system 104 can include attribute descriptor types to indicateinformation for a specific entity or a specific object event.

To illustrate, the digital analytics system 104 can include attributedescriptor types to indicate information for, but not limited to, a typeof digital entity, a digital-entity-creation time, anobject-event-occurrence time, or an object-event type. Utilizing theattribute descriptor types in the domain-event object schema, a digitalanalytics system 104 can provide information for a specific entity orspecific object event within a domain-event object for the specificentity or the specific object event. Additionally, in some instances,the digital analytics system 104 can include attribute descriptor typesto indicate a language associated with a domain-event object, a storage(or server) address from the originating platform (or environment) ofthe domain-event object, or metadata for the entity or object event.Furthermore, the digital analytics system 104 can also include attributedescriptor types to indicate an application (or plug in) that handlesthe entity or object event, a session ID or keys associated with theentity or object event, or other configuration flags (e.g., whethersetup is required for the entity, whether a selection of an entity isrequired for the domain-event object).

In one or more embodiments, the digital analytics system 104 includessuch logic conditions within a domain-event object schema for each typeof domain-event object. In some instances, the digital analytics system104 can utilize the logic conditions from domain-event-listenerconditions within a domain-event object schema to check for (or listenfor) information of the entity, information of an object event, and/orwith one or more attribute descriptors. For example, the digitalanalytics system 104 can utilize a logic condition from thedomain-event-listener condition to listen for a specific creation timeor occurrence time.

Furthermore, in one or more embodiments, the digital analytics system104 includes application data within a domain-event object schema. Toillustrate, the digital analytics system 104 can generate a domain-eventobject schema to include definitions and references for an applicationutilized for a given entity represented by the domain-event objectschema. Indeed, the application data can include definitions that enablea system to utilize functions of the application in relation to theentity identified by the domain-event object schema.

As an example, a domain-event object schema for an e-mail entity caninclude application data for an e-mail application that is utilized tocreate, transmit, and/or view e-mails. The digital analytics system 104can utilize the application data within the domain-event object for thee-mail entity to utilize the e-mail application to perform platformaction in relation to the e-mail entity (upon identifying a domain-eventobject from the domain-event object schema with a domain-eventlistener).

In some embodiments, the digital analytics system 104 utilizes adomain-event object schema that formats domain-event objects into JSONfiles (or files for another structured format markup language orschema). For instance, the digital analytics system 104 can utilizefields of a JSON file to represent fields for the entity type,object-event type, and various other attribute descriptor typesdescribed above. In one or more embodiments, the digital analyticssystem 104 includes information for the entity type, object-event type,and the various other attribute descriptor types by populatinginformation within JSON fields.

As mentioned above, the digital analytics system 104 can generate (andpair together) domain-event-listener rules and platform actions for adomain-event listener based on received domain-event-listener conditionand platform action selections. In particular, the digital analyticssystem 104 can receive selections for domain-event-listener conditionsand platform actions from an administrator device 112 within a graphicaluser interface. Then, the digital analytics system 104 can utilizedomain-event-listener rules (from the selected domain-event-listenerconditions) and selected platform actions to listen for domain-eventobjects in a multi-platform data stream that satisfy thedomain-event-listener rules. Indeed, the digital analytics system 104can also perform the selected platform actions in relation to theidentified domain-event objects.

For example, FIG. 4 illustrates a graphical user interface in which anadministrator device displays selectable domain-event-listenerconditions and selectable platform-action options. As shown in FIG. 4 ,the digital analytics system 104 provides, for display within agraphical user interface 402 of an administrator device 404, selectabledomain-event-listener conditions 406. Indeed, as shown in FIG. 4 , thedigital analytics system 104 can receive, from the administrator device404, selections of an attribute corresponding to a domain-event objectas described above (e.g., an object-event type, an entity type) withinthe selectable domain-event-listener conditions 406. Additionally, asillustrated in FIG. 4 , the digital analytics system 104 can alsoreceive, from the administrator device 404, logic conditions in relationto the domain-event object attribute within the selectabledomain-event-listener conditions 406. Furthermore, as also illustratedin FIG. 4 , the digital analytics system 104 can receive, from theadministrator device 404, values for the selected domain-event objectattribute for the logic conditions within the selectabledomain-event-listener conditions 406.

Upon receiving a selection of the domain-event object attribute,condition logic, and a value for the domain-event object attributewithin the selectable domain-event-listener conditions 406, the digitalanalytics system 104 can utilize the selections as domain-event-listenerrules. As an example, as shown in FIG. 4 , the digital analytics system104 can receive, as a domain-event-listener condition within theselectable domain-event-listener conditions 406, a condition thatlistens for object events (e.g., “event_type”) that matches with (e.g.,“is equal to”) an object event of “activated.” As further shown in FIG.4 , the digital analytics system 104 can add the above-mentioneddomain-event-listener condition, selected from the selectabledomain-event-listener conditions 406, as a domain-event-listener rule ina set of domain-event-listener rules 408.

In some embodiments, the digital analytics system 104 provides theselectable domain-event-listener conditions 406 for display within thegraphical user interface 402 of the administrator device 404 bypopulating the selectable options (e.g., in a drop-down menu, as radiobuttons) utilizing information from a domain-event object schema of aselected entity (or domain-event object). In particular, the digitalanalytics system 104 can receive a request to generatedomain-event-listener rules for a particular entity or domain-eventobject. Then, the digital analytics system 104 can provide theselectable domain-event-listener conditions 406 for display within thegraphical user interface 402 by including values (or information) forthe various attributes and logic conditions from the domain-event objectschema (as described above) into the selectable domain-event-listenerconditions 406.

To illustrate, in reference to FIG. 4 , the digital analytics system 104can identify that the particular domain-event object includes the objectevents “activated,” “deactivated,” “published,” and “shared” within adomain-event object schema. Accordingly, as shown in FIG. 4 , thedigital analytics system 104 provides, for display, the object events“activated,” “deactivated,” “published,” and “shared” as the selectableoptions for “event_type” within the selectable domain-event-listenerconditions 406. Indeed, the digital analytics system 104 can populatefields of various domain-event object attribute types within selectableoptions of a graphical user interface utilizing a domain-event objectschema.

As mentioned above, in one or more embodiments, the digital analyticssystem 104 provides an option to select a number ofdomain-event-listener conditions (e.g., as a combination). For example,as shown in FIG. 4 , the digital analytics system 104 provides aselectable option 410 to add additional domain-event-listenerconditions. Upon receiving a selection of the selectable option 410, thedigital analytics system 104 can receive, via the administrator device404, a combination of domain-event-listener conditions that are combinedusing operational logic relationships (e.g., an “and” operator or an“or” operator).

As further shown in FIG. 4 , the digital analytics system 104 provides,for display within a graphical user interface 402 of an administratordevice 404, platform-action options 412 for a platform action to beperformed upon satisfaction of the domain-event-listener conditionsselected from the selectable domain-event-listener conditions 406. Inparticular, as shown in FIG. 4 , the digital analytics system 104provides, for display, the platform-action options 412 that can beselected in association with the selectable domain-event-listenerconditions 406.

Upon receiving a selection of one or more platform actions from theplatform-action options 412, the digital analytics system 104 cangenerate a pairing between platform actions 414 and thedomain-event-listener rules 408 (e.g., from the selecteddomain-event-listener conditions). Indeed, although FIG. 4 illustratesthe platform-action options 412 as an option to perform a task totransmit an electronic communication (e.g., an e-mail), the digitalanalytics system 104 can include various platform actions (in accordancewith one or more embodiments herein) within the platform-action options412.

In one or more embodiments, the digital analytics system 104 can storethe selected domain-event-listener rules and platform actions that areassociated with (or paired to) the domain-event-listener rules (e.g., toinitiate the platform actions upon satisfaction of the listener rules).Furthermore, the digital analytics system 104 can utilize a domain-eventlistener to compare (or check) incoming domain-event objects within amulti-platform data stream to the stored pairings ofdomain-event-listener rules and platform actions. In particular, thedigital analytics system 104 identifies domain-event objects thatsatisfy the domain-event-listener rules and performs the paired platformaction in relation to the entity indicated by the identifieddomain-event object.

As mentioned above, the digital analytics system 104 can utilize domainevent objects, configured domain-event-listener rules, and amulti-platform data stream to communicate between multiple systems (thatinclude one or more platforms) and take multi-platform aware actions.For example, FIG. 5 illustrates multiple computing systems respectivelyidentifying domain-event objects from a multi-platform data stream anddynamically performing platform actions in response to platform actionstaken on other computing systems.

Indeed, as shown in FIG. 5 , the digital computing system A (e.g., thedigital analytics system 104) can identify a domain-event object 1 fromthe multi-platform data stream 502 (utilizing domain-event-listenerrules). Then, as illustrated in FIG. 5 , the digital computing system Aperforms a platform action based on the identified domain-event object 1in an act 504. Upon performing the platform action in the act 504, thedigital computing system A also generates and provides a domain-eventobject N 506 generated for the platform action performed in the act 504.Indeed, the domain-event object 506 indicates that a platform action wasperformed as described above. As shown in FIG. 5 , the digital computingsystem A provides the domain-event object 506 to the multi-platform datastream 502.

Then, as shown in FIG. 5 , the digital computing system B identifiesthat a domain-event object N matches domain-event-listener rulescorresponding to the digital computing system B within themulti-platform data stream 502. Based on identifying the domain-eventobject N (that indicates the platform action from the digital computingsystem A), the digital computing system B performs a platform action inact 508. Indeed, the platform action in the act 508 is in response tothe domain-event object N. Furthermore, as shown in FIG. 5 , the digitalcomputing system B generates and provides a domain-event object 510 uponperforming the platform action in the act 508. For instance, thedomain-event object 510 indicates that a platform action was performedby the digital computing system B. Lastly, as shown in FIG. 5 , thedigital computing system B provides the domain-event object 510 to themulti-platform data stream 502.

In one or more embodiments, the digital computing systems A and Bcontinuously identify domain-event objects in the multi-platform datastream 502, perform platform actions, and provide domain-event objectsfor those platform actions such that the multiple digital computingsystems A and B can perform dynamic actions that account for actions inother systems. Although FIG. 5 illustrates two digital computingsystems, the digital analytics system 104 can utilize domain-eventobjects to communicate with various numbers of platforms or systems (orto communicate between various platforms or systems) to perform platformactions in accordance with one or more embodiments herein. Indeed, thevarious digital computing systems can utilize the domain-event objectsand multi-platform data stream to take a various combination of actionsthat account for and utilize actions taken in other platform systems.

To illustrate, in some instances, the digital analytics system 104 canreceive a digital survey response from a respondent device. Uponreceiving the digital survey response, the digital analytics system 104can generate a domain-event object to indicate that a digital surveyresponse has been received and provide the domain-event object into amulti-platform data stream. Then, a digital computing system thatmanages technical support tickets may identify the domain-event objectof the survey response and analyze the survey response referenced in thedomain-event object to identify that a technical support issue wasmentioned in the survey response. Subsequently, the digital computingsystem that manages technical support tickets can generate a supportticket for the user corresponding to the survey response. Additionally,in some cases, another digital computing system that manages electroniccommunications may also identify the same domain-event object. Uponidentifying the domain-event object, the digital computing system thatmanages electronic communications can transmit an electroniccommunication to an administrator device to provide the digital surveyresponse content (from the domain-event object) to the administratordevice. In some embodiments, both the digital computing systems formanaging technical support tickets and electronic communications alsogenerate domain-event object based on their respective platform actions.

As another example, a first digital computing system (e.g., the digitalanalytics system 104) can track and generate user experience statisticson a graphical user interface (e.g., a reporting user interface). In theexample, the user experience statistics can be categorized by the typeof operating software is utilized in user computing devices. A seconddigital computing system (e.g., using a third-party platform) may handlethe operating software on user computing devices. The second digitalcomputing system can complete software updates on the user computingdevices and generate domain-event objects to indicate the softwareupdates. These domain-event objects can be identified by the firstdigital computing system and utilized to determine which user computingdevices have updated software. As a result, the first digital computingsystem can recategorize the user experience statistics experiencedwithin different operating software versions within its reporting userinterface based on the changes identified from the domain-event objectsthat were created by the second digital computing system.

Additionally, as another example, a first digital computing systemwithin the digital analytics system 104 can receive updates to usersettings and/or account information. Then, the first digital computingsystem can generate a domain-event object to indicate the updates touser settings and/or account information. Subsequently, one or moreother digital computing systems can identify the domain-event objectand, in response, can trigger a platform process to reflect usersettings and/or account information within their storage to reflect theupdated user settings and/or account information from the digitalcomputing system that transmitted the domain-event object.

Furthermore, as another example, a first digital computing system (e.g.,the digital analytics system 104) can receive data for a creation of anew user account (e.g., a new employee or customer) within a useraccount management platform. Subsequently, the first digital computingsystem can generate a domain-event object to indicate the creation ofthe new user account. Moreover, one or more other digital computingsystems can identify the domain-event object and, in response, cantrigger a platform action to schedule and/or transmit a digital surveyto the user account (e.g., via email, instant message).

In addition, as another example, a first digital computing system canreceive a data indication that a marketing email was opened by a usercorresponding to a user account. In response, the first digitalcomputing system can generate a domain-event object to indicate acomputing device associated with the user account viewed the marketingemail. In turn, one or more other digital computing systems can identifythe domain-event object and, in response, trigger a platform action toupdate metadata records for the user account to indicate the user'sinterest in the content (e.g., a product, a service, an event) presentedwithin the marketing email.

Moreover, as an additional example, a first digital computing system canreceive a completed digital survey with a digital survey score.Furthermore, the first digital computing system can generate a domainevent object that indicates the completion of the digital survey andincludes the digital survey score. One or more other digital computingsystems can identify the domain-event object and analyze the digitalsurvey score. For example, the one or more other digital computingsystems can analyze the digital survey score from the domain-eventobject and determine that the digital survey indicates a negativeexperience (e.g., the score does not satisfy a threshold score). Upondetermining that the completed digital survey from the domain-eventobject constitutes a negative experience, the one or more othercomputing systems can configure a ticket (e.g., as a to-do task, emailevent, scheduled electronic meeting) to follow up with a user associatedwith the user account corresponding to the completed digital survey(e.g., to determine the reasons for the negative experience).

As mentioned above, upon identifying (or receiving) a domain-eventobject, the digital analytics system 104 can perform a platform actionthat is a reaction to the domain-event object. In particular, thedigital analytics system 104 can perform a platform action reflects (oraccounts for) an object event and entity indicated by a domain-eventobject. Indeed, the digital analytics system 104 (or another digitalcomputing system) can perform various combinations of platform actions.In many cases, the platform actions can be specific to adigital-analytics platform of the digital analytics system 104.

For example, as shown in FIG. 6 , the digital analytics system 104 canperform platform actions, such as, but not limited to, transmitting anelectronic communication, configuring a ticket, triggering a platformprocess, modifying a platform workflow, updating a digital reportinginterface, or modifying a platform parameter within thedigital-analytics platform to reflect an identified domain-event object.Specifically, as illustrated in FIG. 6 , the digital analytics system104 can identify a domain-event object 602 that includes an entityidentifier 604 and an object event 606 (e.g., utilizing a domain-eventlistener with domain-event-listener rules as described above). Then, asshown in FIG. 6 , the digital analytics system 104 can perform aplatform action in an act 608 based on the domain-event object 602.

As shown in FIG. 6 , the digital analytics system 104 can transmit anelectronic communication in an act 610 based on the identifieddomain-event object 602. For example, the digital analytics system 104can utilize an identified object event within a domain-event object totransmit an electronic communication reflecting the object event. Insome cases, the digital analytics system 104 can transmit an electroniccommunication (e.g., SMS message, instant message, e-mail, social mediaposts) to an administrator device that notifies or indicates a user ofthe object event that has occurred at one or more digital platformapplications. Indeed, the digital analytics system 104 can includeinformation corresponding to the domain-event object within theelectronic communication. For example, the digital analytics system 104can auto populate portions of an electronic communication based on adomain-event object as described below (e.g., in relation to FIG. 8A).In addition, the digital analytics system 104 can generate adomain-event object to indicate the transmitted electroniccommunication.

As further shown in FIG. 6 , the digital analytics system 104 cantrigger a platform process in an act 612 based on the identifieddomain-event object 602. For instance, the digital analytics system 104can initiate a process task within one or more platforms based onidentifying the domain-event object. In some embodiments, the digitalanalytics system 104 triggers a process task in response to identifyinga domain-event object, such as, but not limited to, compressing data,performing a data backup, importing and/or exporting of data, encryptingdata, aggregating digital survey data, initializing a digital surveyanalysis, or initializing a machine learning model based on thedomain-event object. For example, the digital analytics system 104 canutilize information from the object event of the entity and/or a changedstate of an entity in relation to the object event to trigger one of theabove-mentioned processes. Moreover, the digital analytics system 104can generate a domain-event object to indicate the triggering of theplatform process.

As also illustrated in FIG. 6 , the digital analytics system 104 canmodify a workflow in an act 614 based on the identified domain-eventobject 602. For instance, the digital analytics system 104 can modify aworkflow by modifying workflows, such as, but not limited to, a networkpath of one or more data packets, modify a storage location for one ormore processes, add or remove data analysis processes between workflowsthat prepare digital data (e.g., digital survey responses, electroniccommunications) for a digital reporting user interface. Additionally,the digital analytics system 104 can generate a domain-event object toindicate the workflow modification.

Moreover, as shown in FIG. 6 , the digital analytics system 104 canupdate a digital reporting user interface in an act 616 based on theidentified domain-event object 602. In one or more embodiments, thedigital analytics system 104 updates (or modifies) a digital reportinguser interface based on a domain-event object by utilizing informationidentified within the domain-event object. For example, the digitalanalytics system 104 can perform updates, such as, but not limited to,restructuring the location of information within a digital reportinguser interface based on the domain-event object, modifying bounds ofdata in digital charts based on changes identified in domain-eventobjects, or modifying data categories within a digital reporting userinterface based on the domain-event object. In addition, the digitalanalytics system 104 can generate a domain-event object to indicate theupdate to the digital reporting user interface.

As further illustrated in FIG. 6 , the digital analytics system 104 canmodify parameters in an act 618 based on the identified domain-eventobject 602. For example, the digital analytics system 104 can utilize adomain-event object to modify parameters of various models within thedigital analytics system 104. To illustrate, the digital analyticssystem 104 can modify training and/or tuning parameters of machinelearning models that analyze digital surveys and/or digital userexperiences based on data changes indicated by domain-event objects(from other systems). The digital analytics system 104 can also modifyparameters, such as, but not limited to, parameters that configure datareporting preferences, parameters that control digital surveytransmission frequencies, or parameters that control digital responseanalysis frequencies. Moreover, the digital analytics system 104 cangenerate a domain-event object to indicate the modified parameters.

Furthermore, as shown in FIG. 6 , the digital analytics system 104 canconfigure a ticket in an act 620 based on the identified domain-eventobject 602. For instance, in one or more embodiments, the digitalanalytics system 104 responds to an occurrence from another computingsystem that is identified in the domain-event object by configuring aticket that indicates and tracks tasks that need to be performed for theoccurrence reflected in the domain-event object. For instance, thedigital analytics system 104 can identify a domain-event object thatidentifies a security breach in a third-party platform (of a third-partycomputing system) and, in response, the digital analytics system 104 canconfigure a ticket (e.g., technical support ticket) that identifies thesecurity breach and tasks that need to be completed by a technicalsupport device. Additionally, the digital analytics system 104 cangenerate a domain-event object to indicate the configured ticket.

In one or more embodiments, the digital analytics system 104 can utilizea domain-event object to notify computing systems of changes to varioustypes of data and also perform platform actions for various types ofdata. For example, the digital analytics system 104 can utilizedomain-event objects to identify (or communicate changes or updates of)data such as, but not limited to, data representing digital surveys,multi-party conversations, digital survey invitations, digitalimpressions, digital survey assessments, dashboards, reports,benchmarks, statistical models, topic models, triggers, tasks,workflows, tickets, digital action plans, digital calendar events,and/or machine learning data (e.g., machine learning events, machinelearning outputs, automated machine learning tasks, and/or dataartifacts). Moreover, the digital analytics system 104 can also utilizedomain-event objects to identify (or communicate changes or updates of)data such as, but not limited to, datasets, storage hierarchies, userdata, role data, organizational data, directories, segments, mailinglists, profiles, digital reward accounts, touchpoints, programs,projects, templates, libraries, notifications, and electronic messages.

Additionally, the digital analytics system 104 can also perform platformactions that utilize third-party platforms. For instance, the digitalanalytics system 104 can perform a platform action that initiates orutilizes an API call or plugin from a third-party platform. Toillustrate, the digital analytics system 104 can transmit an electroniccommunication through a third-party application that sharescommunication to the administrator device or a plurality of computingdevices. Moreover, the digital analytics system 104 can perform aplatform action that initiates or utilizes an API call or plugin togenerate reports from data provided by the digital analytics system 104.Indeed, adding platform actions for third-party platforms to pair withdomain-event-listener rules is described in greater detail below (e.g.,in relation to FIGS. 7A-7C).

Furthermore, in some embodiments, the digital analytics system 104perform multiple platform actions (e.g., a chain of platform actions)based on identifying a domain-event object. To illustrate, thedomain-event object can include a pairing between domain-event-listenerrules and multiple platform action selections. In such a case, thedigital analytics system 104 can perform each of the platform actionsassociated with identifying a domain-event object. For example, thedigital analytics system 104 can transmit an electronic message, updatea digital reporting user interface, and modify parameters uponidentifying a single domain-event object.

As mentioned above, the digital analytics system 104 can provide, fordisplay within a graphical user interface, selectable options to selectdomain-event-listener conditions and platform action pairings. Inaddition, the digital analytics system 104 can also provide, for displaywithin a graphical user interface, selectable options to select platformactions that utilize third-party platforms. For example, FIGS. 7A-7Cillustrate the digital analytics system 104 providing, for displaywithin a graphical user interface, selectable options to select platformactions that utilize third-party platforms in connection todomain-event-listener conditions.

For instance, as shown in FIG. 7A, the digital analytics system 104provides, for display within a graphical user interface 702 of anadministrator device 704, selectable domain-event-listener conditions706 and a platform-action option 708 (as described above in relation toFIG. 4 ). Upon receiving an indication of a selection of theplatform-actions option 708, the digital analytics system 104 canprovide, for display within an application selection graphical userinterface, options to select a platform action application (e.g., athird-party application or an internal application) to perform theplatform action. Indeed, FIG. 7B illustrates the digital analyticssystem 104, providing application options 710 to select a platformaction application for display within an application selection graphicaluser interface 711 in response to receiving a request to add a platformaction to one or more domain-event-listener conditions (within theadministrator device 704).

As shown in FIG. 7B, the digital analytics system 104 can provide theapplication options 710 to select platform actions and an accompanyingthird-party application to perform that platform action from theapplication selection graphical user interface 711. Indeed, the digitalanalytics system 104 can utilize the selected platform action byrequesting (or initiating) a third-party platform application to performthe platform action when a domain-event object that satisfies selecteddomain-event-listener rules is detected. Furthermore, the digitalanalytics system 104 can utilize (or provide) a wide variety of platformactions from third-party platform sources for selection in connection todomain-event-listener rules.

Furthermore, as shown in FIG. 7C, the digital analytics system 104 alsoprovides, for display within a graphical user interface 712 of theadministrator device 704, a list of created domain-event objectlisteners and platform actions with options to activate or deactivatethe domain-event object listeners (e.g., toggle button for on or off).In particular, as shown in FIG. 7C, the digital analytics system 104provides, for display within a graphical user interface 712,domain-event-object-listener-action-pair names 714, the type ofdomain-event object that is being tracked in a trigger column 716, andthe type of platform action that will be performed upon detecting adomain-event object in a task column 718.

As illustrated in FIG. 7C, the digital analytics system 104 provides,for display within the graphical user interface 712, a selectable option713 to create a new platform action. Indeed, upon indication of aselection of the selectable option 713, the digital analytics system 104can provide, for display within a graphical user interface, selectableoptions to generate a domain-event-object listener and correspondingplatform actions. More specifically, the digital analytics system 104can provide, for display within a graphical user interface, selectableoptions to select one or more domain-event-listener conditions andcorresponding platform actions in accordance with one or moreembodiments.

Additionally, as shown in FIG. 7C, the digital analytics system 104provides, for display within the graphical user interface 712, aselectable option 720 to toggle domain-event-object listener andplatform action pairings. Indeed, upon receiving an indication of aselection of the selectable option 720, the digital analytics system 104can activate and/or deactivate a particular domain-event listener andits corresponding platform action(s). Additionally, the digitalanalytics system 104 also provides, for display within the graphicaluser interface 712, a selectable option 722 to modify a particulardomain-event listener and its corresponding platform action(s). Forexample, upon receiving an indication of a selection of the selectableoption 722, the digital analytics system 104 can provide options toselect additional domain-event-listener conditions, removedomain-event-listener conditions, modify domain-event-listenerconditions, add platform actions, remove platform actions, or modifyplatform actions in accordance with one or more embodiments.

In some embodiments, the digital analytics system 104 provides, fordisplay within a graphical user interface, platform action setup options(e.g., within templates) that include fields that auto populateutilizing domain-event objects. For example, FIG. 8A illustrates thedigital analytics system 104 providing, for display within a graphicaluser interface 802 of an administrator device 804, platform action setupoptions for an electronic communication transmittal action. Inparticular, FIG. 8A illustrates the digital analytics system 104providing, for display within the graphical user interface 802 of theadministrator device 804, platform action setup options to configure ane-mail task for a domain-event object.

As shown in FIG. 8A, the digital analytics system 104 can providereference options that provide pointers to attribute information for atarget domain-event object. Indeed, the digital analytics system 104 cangenerate pointers to information concerning a target domain-event objectby inserting a domain-event object reference 808 within a text body 810of an e-mail. For example, as shown in FIG. 8A, the digital analyticssystem 104 can insert a domain-event object reference 808 to replacetext within the text body 810 with an object-event type associated witha domain-event object that triggers the e-mail platform action (e.g.,upon receiving an indication of an interaction with a domain-eventobject reference selector 806).

As also shown in FIG. 8A, the digital analytics system 104 can insert adomain-event object reference 812 to replace text within the text body810 with a status corresponding to the domain-event object. Indeed, thedigital analytics system 104 can utilize various attribute types or datafrom a domain-event object (in accordance with one or more embodiments)within the domain-event object reference pointers (e.g., by utilizing adropdown list and/or a radio button list of domain-event object datatypes).

As another example, FIG. 8B illustrates the digital analytics system 104providing, for display within a graphical user interface 814 of theadministrator device 804, platform action setup options (e.g., withintemplates) for configuring a ticket based on a domain-event object. Inparticular, as shown in FIG. 8B, the digital analytics system 104 canalso provide, for display within the graphical user interface 814,fields that include selectable options to auto populate data withinformation from a target domain-event object within a configurableticket. Indeed, as illustrated in FIG. 8B, the digital analytics system104 can insert a domain-event object reference 816 within data fields ofa configurable ticket such that the domain-event object reference 816 isreplaced with information from a corresponding domain-event object(e.g., a service experience referenced within the domain-event object).

Although FIGS. 8A and 8B illustrate the digital analytics system 104utilizing an e-mail setup and a ticket configuration setup as theplatform action, in some embodiments, the digital analytics system 104utilizes various attribute types or data from a domain-event object (asdescribed above) within the domain-event object reference pointers insetup options for various other platform actions.

Additionally, although FIGS. 7A-7C and 8A-8B illustrate one or moreembodiments of a graphical user interface, the digital analytics system104 can provide a graphical user interface (for display on a computingdevice) that includes various user interface attributes. For example,the digital analytics system 104 can provide a graphical user interfacethat includes various filtering, merging, and/or joining options for thedomain-event-object listener conditions and/or platform actions. In somecases, the digital analytics system 104 can provide a graphical userinterface that includes color-based or other visual updates to thegraphical user interface for the selectable options corresponding to thedomain-event-object listener conditions and/or platform actions.Moreover, the digital analytics system 104 can provide user interfaceelements, such as, but not limited to, drop down elements, graphs,tables, charts, sliding tools, text input elements, radio buttons, orother user interface controls for the selectable options correspondingto the domain-event-object listener conditions and/or platform actions.Additionally, in some embodiments, the digital analytics system 104 canalso provide selectable options within a graphical user interface basedon various user roles, user permissions, and/or product featurescorresponding to an administrator device (or user account).

Turning now to FIG. 9 , additional detail will be provided regardingcomponents and capabilities of one or more implementations of thedigital analytics system 104. In particular, FIG. 9 illustrates anexample environment 900 in which the digital analytics system 104 isexecuted. As shown by the implementation of FIG. 9 , the environment 900includes or hosts multi-platform data stream 902, a digital messageplatform 904, a domain-event listener 906, a platform actions manager908, third-party platforms 910, and a network 912.

As just mentioned, and as illustrated in the implementation of FIG. 9 ,the environment 900 includes the multi-platform data stream 902 and thedigital message platform 904. For example, the multi-platform datastream 902 can facilitate the receiving, storage, and/or transmission ofdomain-event objects between internal platform systems of the digitalanalytics system 104 and/or domain-event objects from third-partyplatforms 910 as described above (e.g., in relation to FIGS. 1, 2, and 3). In addition, the digital message platform 904 can receive, store,and/or transmit domain-event objects between internal platform systemsof the digital analytics system 104 as described above (e.g., inrelation to FIGS. 1, 2, and 3 ).

Furthermore, as illustrated in the implementation of FIG. 9 , theenvironment 900 includes the domain-event listener 906. The domain-eventlistener 906 can detect domain-event objects within the digital messageplatform 904 (or the multi-platform data stream 902) and check thedomain-event objects against sets of domain-event listener rules asdescribed above (e.g., in relation to FIGS. 2-5 ). Upon identifying adomain-event object that satisfies a set of domain-event listener rules,the domain-event listener 906 provides the identified domain-eventobject to the platform action manager 908 as described above (e.g., inrelation to FIGS. 2-5 ). The domain-event listener 906 can listen fordomain-event objects from both internal platforms and/or third-partyplatforms 910 in the multi-platform data stream 902 and/or the digitalmessage platform 904 as described above (e.g., in relation to FIGS. 1-5).

As further illustrated in FIG. 9 , the environment 900 includes theplatform action manager 908. Indeed, the platform action manager 908 canreceive domain-event objects and identify information corresponding tothe domain-event objects (e.g., entity identifiers, object events) asdescribed above (e.g., in relation to FIGS. 2 and 5-6 ). Furthermore,the platform action manager 908 can perform a platform action thatreflects the domain-event object identified by the domain-event listener906 as described above (e.g., in relation to FIGS. 2 and 5-6 ). Inparticular, the platform action manager 908 can perform platformactions, such as, but not limited to, transmitting an electroniccommunication, configuring a ticket, triggering a platform process,modifying a platform workflow, updating a digital reporting interface,or modifying a platform parameter within the digital-analytics platformto reflect an identified domain-event object as described above (e.g.,in relation to FIGS. 2 and 5-6 ). Furthermore, the platform actionmanager 908 can generate and transmit a domain-event object for theplatform action to the multi-platform data stream 902 and/or the digitalmessage platform 904 as described above (e.g., in relation to FIGS. 2and 5-6 ).

Moreover, as illustrated in the implementation of FIG. 9 , theenvironment 900 includes the third-party platforms 910. For example, thethird-party platforms 910 can communicate with components of the digitalanalytics system 104 through the multi-platform data stream 902 and/orthe digital message platform 904 via a network 912 (e.g., a network asdescribed in FIG. 1 ). Indeed, the third-party platforms 910 can includedomain-event listeners to listen for domain-event objects in themulti-platform data stream 902 and/or the digital message platform 904and perform platform actions based on identified domain-event objects asdescribed above (e.g., in relation to FIGS. 2-6 ). Moreover, computingsystems for the third-party platforms 910 can transmit domain-eventobjects to the multi-platform data stream 902 and/or the digital messageplatform 904 such that the domain-event listener 906 and the platformaction manager 908 can react to the third-party platform domain-eventobjects as described above (e.g., in relation to FIGS. 2 and 5-6 ).

Turning now to FIG. 10 , this figure illustrates a flowchart of a seriesof acts 1000 of performing platform actions utilizing domain-eventobjects in accordance with one or more embodiments. While FIG. 10illustrates acts according to one embodiment, alternative embodimentsmay omit, add to, reorder, and/or modify any of the acts shown in FIG.10 . The acts of FIG. 10 can be performed as part of a method.Alternatively, a non-transitory computer readable storage medium cancomprise instructions that, when executed by one or more processors,cause a computing device to perform the acts depicted in FIG. 10 . Instill further embodiments, a system can perform the acts of FIG. 10 .

As shown in FIG. 10 , the acts 1000 include an act 1010 of receivingdomain-event objects in a multi-platform data stream. In particular, theact 1010 can include receiving, within a multi-platform data stream, aset of domain-event objects. For example, a domain-event object caninclude an entity identifier and object event. Furthermore, the act 1010can include identifying, from a schema library for a multi-platform datastream, a domain-event object schema for a domain-event object to accessdomain-event-listener conditions corresponding to the domain-eventobject. In addition, the act 1010 can include generating a newdomain-event object, generating a domain-event schema for the newdomain-event object having domain-event-listener conditions to identifythe new domain-event object within a multi-platform data stream, andproviding the domain-event object schema to a schema library for themulti-platform data stream.

As further shown in FIG. 10 , the acts 1000 include an act 1020 ofidentifying a domain-event object based on domain-event-listener rules.In particular, the act 1020 can include identifying, from a set ofdomain-event objects, a domain-event object based on an entityidentifier for the domain-event object satisfying a set ofdomain-event-listener rules for a digital-analytics platform.Furthermore, the act 1020 can include determining that an entityidentifier satisfies a given domain-event-listener rule from a set ofdomain-event-listener rules by determining that the entity identifiersatisfies a logic condition for a type of digital entity, adigital-entity-creation time, an object-event-occurrence time, or anobject-event type. In addition, the act 1020 can include accessingcontent corresponding to an entity identifier and an object event of adomain-event object by utilizing the entity identifier as a reference.

Furthermore, the act 1020 can include identifying an object event for adomain-event object. For example, identifying an object event caninclude identifying a creation of, an assignment of, a transmission of,a modification to, an interaction with, a publication of, an update of,a sharing of, a subscription to, an unsubscription to, or a rejection ofa digital entity corresponding to an entity identifier. Furthermore, adigital entity can include a contact, a form, a ticket, a response, adistribution, a survey invitation, a list member, or a segment member.In addition, the act 1020 can include determining that an identifieddomain-event object corresponds to a third-party platform differing froma digital-analytics platform.

Additionally, the act 1020 can include providing, for display within agraphical user interface of an administrator device, a selectabledomain-event-listener condition in relation to an entity identifier of adomain-event object. Moreover, the act 1020 can include receiving, froman administrator device, an indication of a selection of a selectabledomain-event-listener condition and, based on the selection of theselectable domain-event-listener condition, adding the selectabledomain-event-listener condition as a domain-event-listener rule to a setof domain-event-listener rules. Furthermore, the act 1020 can includeproviding, for display within a graphical user interface of anadministrator device, a platform-action option for a platform action tobe performed upon satisfaction of a domain-event-listener condition. Inaddition, the act 1020 can include receiving, from an administratordevice, an indication of a selection of a platform-action option and,based on a selection of the platform-action option, associating theplatform action with a set of domain-event-listener rules such that theplatform action is performed upon satisfying a domain-event-listenercondition.

As further shown in FIG. 10 , the acts 1000 include an act 1030 ofperforming a platform action based on the domain-event object. Inparticular, the act 1030 can include performing a platform action withina digital-analytics platform based on an entity identifier and an objectevent for a domain-event object. For example, a platform action caninclude transmitting an electronic communication, configuring a ticket,triggering a platform process, modifying a platform workflow, updating adigital reporting interface, or modifying a platform parameter within adigital-analytics platform to reflect an identified domain-event object.Furthermore, the act 1030 can include performing a platform actionwithin a digital-analytics platform in response to a third-partyplatform action taken on a third-party platform as indicated by anidentified domain-event object.

Moreover, the act 1030 can include, in response to performing a platformaction, generating an additional domain-event object comprising anadditional entity identifier and an additional object eventcorresponding to the platform action. In addition, the act 1030 caninclude providing an additional domain-event object to a multi-platformdata stream. In some instances, the act 1030 can include identifying anadditional platform action corresponding to an additional platform takenin response to a domain-event object.

Embodiments of the present disclosure may comprise or utilize aspecial-purpose or general-purpose computer including computer hardware,such as, for example, one or more processors and system memory, asdiscussed in greater detail below. Embodiments within the scope of thepresent disclosure also include physical and other computer-readablemedia for carrying or storing computer-executable instructions and/ordata structures. In particular, one or more of the processes describedherein may be implemented at least in part as instructions embodied in anon-transitory computer-readable medium and executable by one or morecomputing devices (e.g., any of the media content access devicesdescribed herein). In general, a processor (e.g., a microprocessor)receives instructions, from a non-transitory computer-readable medium,(e.g., a memory), and executes those instructions, thereby performingone or more processes, including one or more of the processes describedherein.

Computer-readable media can be any available media that can be accessedby a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arenon-transitory computer-readable storage media (devices).Computer-readable media that carry computer-executable instructions aretransmission media. Thus, by way of example, and not limitation,embodiments of the disclosure can comprise at least two distinctlydifferent kinds of computer-readable media: non-transitorycomputer-readable storage media (devices) and transmission media.

Non-transitory computer-readable storage media (devices) includes RAM,ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM),Flash memory, phase-change memory (“PCM”), other types of memory, otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium which can be used to store desired programcode means in the form of computer-executable instructions or datastructures and which can be accessed by a general purpose or specialpurpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data linkswhich can be used to carry desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media tonon-transitory computer-readable storage media (devices) (or viceversa). For example, computer-executable instructions or data structuresreceived over a network or data link can be buffered in RAM within anetwork interface module (e.g., a “NIC”), and then eventuallytransferred to computer system RAM and/or to less volatile computerstorage media (devices) at a computer system. Thus, it should beunderstood that non-transitory computer-readable storage media (devices)can be included in computer system components that also (or evenprimarily) utilize transmission media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general-purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. In one or moreembodiments, computer-executable instructions are executed on ageneral-purpose computer to turn the general-purpose computer into aspecial purpose computer implementing elements of the disclosure. Thecomputer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, or evensource code. Although the subject matter has been described in languagespecific to structural marketing features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the described marketing features oracts described above. Rather, the described marketing features and actsare disclosed as example forms of implementing the claims.

Those skilled in the art will appreciate that the disclosure may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, and the like. The disclosuremay also be practiced in distributed system environments where local andremote computer systems, which are linked (either by hardwired datalinks, wireless data links, or by a combination of hardwired andwireless data links) through a network, both perform tasks. In adistributed system environment, program modules may be located in bothlocal and remote memory storage devices.

Embodiments of the present disclosure can also be implemented in cloudcomputing environments. In this description, “cloud computing” isdefined as a subscription model for enabling on-demand network access toa shared pool of configurable computing resources. For example, cloudcomputing can be employed in the marketplace to offer ubiquitous andconvenient on-demand access to the shared pool of configurable computingresources. The shared pool of configurable computing resources can berapidly provisioned via virtualization and released with low managementeffort or service provider interaction, and then scaled accordingly.

A cloud-computing subscription model can be composed of variouscharacteristics such as, for example, on-demand self-service, broadnetwork access, resource pooling, rapid elasticity, measured service,and so forth. A cloud-computing subscription model can also exposevarious service subscription models, such as, for example, Software as aService (“SaaS”), a web service, Platform as a Service (“PaaS”), andInfrastructure as a Service (“IaaS”). A cloud-computing subscriptionmodel can also be deployed using different deployment subscriptionmodels such as private cloud, community cloud, public cloud, hybridcloud, and so forth. In this description and in the claims, a“cloud-computing environment” is an environment in which cloud computingis employed.

FIG. 11 illustrates a block diagram of an exemplary computing device1100 that may be configured to perform one or more of the processesdescribed above. One will appreciate that one or more computing devicessuch as the computing device 1100 may implement the administrator device112 (as a client device), the respondent devices 110 a-110 n, the serverdevice(s) 102, and/or other devices described above in connection withFIG. 1 . As shown by FIG. 11 , the computing device 1100 can comprise aprocessor 1102, a memory 1104, a storage device 1106, an I/O interface1108, and a communication interface 1110, which may be communicativelycoupled by way of a communication infrastructure 1112. While theexemplary computing device 1100 is shown in FIG. 11 , the componentsillustrated in FIG. 11 are not intended to be limiting. Additional oralternative components may be used in other embodiments. Furthermore, incertain embodiments, the computing device 1100 can include fewercomponents than those shown in FIG. 11 . Components of the computingdevice 1100 shown in FIG. 11 will now be described in additional detail.

In one or more embodiments, the processor 1102 includes hardware forexecuting instructions, such as those making up a computer program. Asan example and not by way of limitation, to execute instructions, theprocessor 1102 may retrieve (or fetch) the instructions from an internalregister, an internal cache, the memory 1104, or the storage device 1106and decode and execute them. In one or more embodiments, the processor1102 may include one or more internal caches for data, instructions, oraddresses. As an example and not by way of limitation, the processor1102 may include one or more instruction caches, one or more datacaches, and one or more translation lookaside buffers (“TLBs”).Instructions in the instruction caches may be copies of instructions inthe memory 1104 or the storage device 1106.

The memory 1104 may be used for storing data, metadata, and programs forexecution by the processor(s). The memory 1104 may include one or moreof volatile and non-volatile memories, such as Random-Access Memory(“RAM”), Read Only Memory (“ROM”), a solid-state disk (“SSD”), Flash,Phase Change Memory (“PCM”), or other types of data storage. The memory1104 may be internal or distributed memory.

The storage device 1106 includes storage for storing data orinstructions. As an example and not by way of limitation, storage device1106 can comprise a non-transitory storage medium described above. Thestorage device 1106 may include a hard disk drive (“HDD”), a floppy diskdrive, flash memory, an optical disc, a magneto-optical disc, magnetictape, or a Universal Serial Bus (“USB”) drive or a combination of two ormore of these. The storage device 1106 may include removable ornon-removable (or fixed) media, where appropriate. The storage device1106 may be internal or external to the computing device 1100. In one ormore embodiments, the storage device 1106 is non-volatile, solid-statememory. In other embodiments, the storage device 1106 includes read-onlymemory (“ROM”). Where appropriate, this ROM may be mask programmed ROM,programmable ROM (“PROM”), erasable PROM (“EPROM”), electricallyerasable PROM (“EEPROM”), electrically alterable ROM (“EAROM”), or flashmemory or a combination of two or more of these.

The I/O interface 1108 allows a user to provide input to, receive outputfrom, and otherwise transfer data to and receive data from the computingdevice 1100. The I/O interface 1108 may include a mouse, a keypad or akeyboard, a touch screen, a camera, an optical scanner, networkinterface, modem, other known I/O devices or a combination of such I/Ointerfaces. The I/O interface 1108 may include one or more devices forpresenting output to a user, including, but not limited to, a graphicsengine, a display (e.g., a display screen), one or more output drivers(e.g., display drivers), one or more audio speakers, and one or moreaudio drivers. In certain embodiments, the I/O interface 1108 isconfigured to provide graphical data to a display for presentation to auser. The graphical data may be representative of one or more graphicaluser interfaces and/or any other graphical content as may serve aparticular implementation.

The communication interface 1110 can include hardware, software, orboth. In any event, the communication interface 1110 can provide one ormore interfaces for communication (such as, for example, packet-basedcommunication) between the computing device 1100 and one or more othercomputing devices or networks. As an example and not by way oflimitation, the communication interface 1110 may include a networkinterface controller (“NIC”) or network adapter for communicating withan Ethernet or other wire-based network or a wireless NIC (“WNIC”) orwireless adapter for communicating with a wireless network, such as aWI-FI.

Additionally, or alternatively, the communication interface 1110 mayfacilitate communications with an ad hoc network, a personal areanetwork (“PAN”), a local area network (“LAN”), a wide area network(“WAN”), a metropolitan area network (“MAN”), or one or more portions ofthe Internet or a combination of two or more of these. One or moreportions of one or more of these networks may be wired or wireless. Asan example, the communication interface 1110 may facilitatecommunications with a wireless PAN (“WPAN”) (such as, for example, aBLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephonenetwork (such as, for example, a Global System for Mobile Communications(“GSM”) network), or other suitable wireless network or a combinationthereof.

Additionally, the communication interface 1110 may facilitatecommunications various communication protocols. Examples ofcommunication protocols that may be used include, but are not limitedto, data transmission media, communications devices, TransmissionControl Protocol (“TCP”), Internet Protocol (“IP”), File TransferProtocol (“FTP”), Telnet, Hypertext Transfer Protocol (“HTTP”),Hypertext Transfer Protocol Secure (“HTTPS”), Session InitiationProtocol (“SIP”), Simple Object Access Protocol (“SOAP”), ExtensibleMark-up Language (“XML”) and variations thereof, Simple Mail TransferProtocol (“SMTP”), Real-Time Transport Protocol (“RTP”), User DatagramProtocol (“UDP”), Global System for Mobile Communications (“GSM”)technologies, Code Division Multiple Access (“CDMA”) technologies, TimeDivision Multiple Access (“TDMA”) technologies, Short Message Service(“SMS”), Multimedia Message Service (“MMS”), radio frequency (“RF”)signaling technologies, Long Term Evolution (“LTE”) technologies,wireless communication technologies, in-band and out-of-band signalingtechnologies, and other suitable communications networks andtechnologies.

The communication infrastructure 1112 may include hardware, software, orboth that couples components of the computing device 1100 to each other.As an example and not by way of limitation, the communicationinfrastructure 1112 may include an Accelerated Graphics Port (“AGP”) orother graphics bus, an Enhanced Industry Standard Architecture (“EISA”)bus, a front-side bus (“FSB”), a HYPERTRANSPORT (“HT”) interconnect, anIndustry Standard Architecture (“ISA”) bus, an INFINIBAND interconnect,a low-pin-count (“LPC”) bus, a memory bus, a Micro Channel Architecture(“MCA”) bus, a Peripheral Component Interconnect (“PCI”) bus, aPCI-Express (“PCIe”) bus, a serial advanced technology attachment(“SATA”) bus, a Video Electronics Standards Association local (“VLB”)bus, or another suitable bus or a combination thereof.

FIG. 12 illustrates an example network environment 1200 of the digitalanalytics system 104. Network environment 1200 includes a client device1206, and a server device 1202 connected to each other by a network1204. Although FIG. 12 illustrates a particular arrangement of clientdevice 1206, server device 1202, and network 1204, this disclosurecontemplates any suitable arrangement of client device 1206, serverdevice 1202, and network 1204. As an example and not by way oflimitation, two or more of the client devices 1206, and server devices1202 may be connected to each other directly, bypassing network 1204. Asanother example, two or more of client devices 1206 and server devices1202 may be physically or logically co-located with each other in whole,or in part. Moreover, although FIG. 12 illustrates a particular numberof client devices 1206, server devices 1202, and networks 1204, thisdisclosure contemplates any suitable number of client devices 1206,server devices 1202, and networks 1204. As an example and not by way oflimitation, network environment 1200 may include multiple client devices1206, server devices 1202, and networks 1204.

This disclosure contemplates any suitable network 1204. As an exampleand not by way of limitation, one or more portions of network 1204 mayinclude an ad hoc network, an intranet, an extranet, a virtual privatenetwork (“VPN”), a local area network (“LAN”), a wireless LAN (“WLAN”),a wide area network (“WAN”), a wireless WAN (“WWAN”), a metropolitanarea network (“MAN”), a portion of the Internet, a portion of the PublicSwitched Telephone Network (“PSTN”), a cellular telephone network, or acombination of two or more of these. Network 1204 may include one ormore networks 1204.

Links may connect client device 1206, and server device 1202 to network1204 or to each other. This disclosure contemplates any suitable links.In particular embodiments, one or more links include one or morewireline (such as for example Digital Subscriber Line (“DSL”) or DataOver Cable Service Interface Specification (“DOCSIS”)), wireless (suchas for example Wi-Fi or Worldwide Interoperability for Microwave Access(“WiMAX”)), or optical (such as for example Synchronous Optical Network(SONET) or Synchronous Digital Hierarchy (“SDH”)) links. In particularembodiments, one or more links each include an ad hoc network, anintranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, aportion of the Internet, a portion of the PSTN, a cellulartechnology-based network, a satellite communications technology-basednetwork, another link, or a combination of two or more such links. Linksneed not necessarily be the same throughout network environment 1200.One or more first links may differ in one or more respects from one ormore second links.

In particular embodiments, client device 1206 may be an electronicdevice including hardware, software, or embedded logic components or acombination of two or more such components and capable of carrying outthe appropriate functionalities implemented or supported by clientdevice 1206. As an example and not by way of limitation, a client device1206 may include any of the computing devices discussed above inrelation to FIG. 11 . A client device 1206 may enable a network user atclient device 1206 to access network 1204.

In particular embodiments, client device 1206 may include a web browser,such as MICROSOFT INTERNET EXPLORER, GOOGLE CHROME, or MOZILLA FIREFOX,and may have one or more add-ons, plug-ins, or other extensions, such asTOOLBAR or YAHOO TOOLBAR. A user at client device 1206 may enter aUniform Resource Locator (“URL”) or other address directing the webbrowser to a particular server (such as server, or a server associatedwith a third-party system), and the web browser may generate a HyperText Transfer Protocol (“HTTP”) request and communicate the HTTP requestto server. The server may accept the HTTP request and communicate toclient device 1206 one or more Hyper Text Markup Language (“HTML”) filesresponsive to the HTTP request. Client device 1206 may render a webpagebased on the HTML files from the server for presentation to the user.This disclosure contemplates any suitable webpage files. As an exampleand not by way of limitation, webpages may render from HTML files,Extensible Hyper Text Markup Language (“XHTML”) files, or ExtensibleMarkup Language (“XML”) files, according to particular needs. Such pagesmay also execute scripts such as, for example and without limitation,those written in JAVASCRIPT, JAVA, MICROSOFT SILVERLIGHT, combinationsof markup language and scripts such as AJAX (Asynchronous JAVASCRIPT andXML), and the like. Herein, reference to a webpage encompasses one ormore corresponding webpage files (which a browser may use to render thewebpage) and vice versa, where appropriate.

In particular embodiments, server device 1202 may include a variety ofservers, sub-systems, programs, modules, logs, and data stores. Inparticular embodiments, server device 1202 may include one or more ofthe following: a web server, action logger, API-request server,relevance-and-ranking engine, content-object classifier, notificationcontroller, action log, third-party-content-object-exposure log,inference module, authorization/privacy server, search module,advertisement-targeting module, user-interface module, user-profilestore, connection store, third-party content store, or location store.Server device 1202 may also include suitable components such as networkinterfaces, security mechanisms, load balancers, failover servers,management-and-network-operations consoles, other suitable components,or any suitable combination thereof.

In particular embodiments, server device 1202 may include one or moreuser-profile stores for storing user profiles. A user profile mayinclude, for example, biographic information, demographic information,behavioral information, social information, or other types ofdescriptive information, such as work experience, educational history,hobbies or preferences, interests, affinities, or location. Interestinformation may include interests related to one or more categories.Categories may be general or specific. Additionally, a user profile mayinclude financial and billing information of users (e.g., respondents,customers).

The foregoing specification is described with reference to specificexemplary embodiments thereof. Various embodiments and aspects of thedisclosure are described with reference to details discussed herein, andthe accompanying drawings illustrate the various embodiments. Thedescription above and drawings are illustrative and are not to beconstrued as limiting. Numerous specific details are described toprovide a thorough understanding of various embodiments.

The additional or alternative embodiments may be embodied in otherspecific forms without departing from its spirit or essentialcharacteristics. The described embodiments are to be considered in allrespects only as illustrative and not restrictive. The scope of theinvention is, therefore, indicated by the appended claims rather than bythe foregoing description. All changes that come within the meaning andrange of equivalency of the claims are to be embraced within theirscope.

What is claimed is:
 1. A computer-implemented method comprising:receiving, within a multi-platform data stream, a set of domain-eventobjects comprising entity identifiers and object events; identifying,from the set of domain-event objects, a domain-event object based on anentity identifier for the domain-event object satisfying a set ofdomain-event-listener rules for a digital-analytics platform;identifying an object event for the domain-event object; and based onthe entity identifier and the object event for the domain-event object,performing a platform action within the digital-analytics platform. 2.The computer-implemented method of claim 1, wherein performing theplatform action comprises transmitting an electronic communication,configuring a ticket, triggering a platform process, modifying aplatform workflow, updating a digital reporting interface, or modifyinga platform parameter within the digital-analytics platform to reflectthe identified domain-event object.
 3. The computer-implemented methodof claim 1, further comprising identifying, from a schema library forthe multi-platform data stream, a domain-event object schema for thedomain-event object to access domain-event-listener conditionscorresponding to the domain-event object.
 4. The computer-implementedmethod of claim 1, wherein identifying the object event comprisesidentifying a creation of, an assignment of, a transmission of, amodification to, an interaction with, a publication of, an update of, asharing of, a subscription to, an unsubscription to, or a rejection of adigital entity corresponding to the entity identifier.
 5. Thecomputer-implemented method of claim 4, wherein the digital entitycomprises a contact, a form, a ticket, a response, a distribution, asurvey invitation, a list member, or a segment member.
 6. Thecomputer-implemented method of claim 1, further comprising: determiningthat the identified domain-event object corresponds to a third-partyplatform differing from the digital-analytics platform; and performingthe platform action within the digital-analytics platform in response toa third-party platform action taken on the third-party platform asindicated by the identified domain-event object.
 7. Thecomputer-implemented method of claim 1, further comprising determiningthat the entity identifier satisfies a given domain-event-listener rulefrom the set of domain-event-listener rules by determining that theentity identifier satisfies a logic condition for a type of digitalentity, a digital-entity-creation time, an object-event-occurrence time,or an object-event type.
 8. The computer-implemented method of claim 1,further comprising: in response to performing the platform action,generating an additional domain-event object comprising an additionalentity identifier and an additional object event corresponding to theplatform action; and providing the additional domain-event object to themulti-platform data stream.
 9. A non-transitory computer-readable mediumstoring instructions that, when executed by at least one processor,cause a computing device to: receive, within a multi-platform datastream, a set of domain-event objects comprising entity identifiers andobject events; identify, from the set of domain-event objects, adomain-event object based on an entity identifier for the domain-eventobject satisfying a set of domain-event-listener rules for adigital-analytics platform; identify an object event for thedomain-event object; and based on the entity identifier and the objectevent for the domain-event object, perform a platform action within thedigital-analytics platform.
 10. The non-transitory computer-readablemedium of claim 9, further comprising instructions that, when executedby the at least one processor, cause the computing device to perform theplatform action by transmitting an electronic communication, configuringa ticket, triggering a platform process, modifying a platform workflow,updating a digital reporting interface, or modifying a platformparameter within the digital-analytics platform to reflect theidentified domain-event object.
 11. The non-transitory computer-readablemedium of claim 9, further comprising instructions that, when executedby the at least one processor, cause the computing device to identify,from a schema library for the multi-platform data stream, a domain-eventobject schema for the domain-event object to accessdomain-event-listener conditions corresponding to the domain-eventobject.
 12. The non-transitory computer-readable medium of claim 9,wherein: the object event comprises a creation of, an assignment of, atransmission of, a modification to, an interaction with, a publicationof, an update of, a sharing of, a subscription to, an unsubscription to,or a rejection of a digital entity corresponding to the entityidentifier; and the digital entity comprises a contact, a form, aticket, a response, a distribution, a survey invitation, a list member,or a segment member.
 13. The non-transitory computer-readable medium ofclaim 9, further comprising instructions that, when executed by the atleast one processor, cause the computing device to determine that theentity identifier satisfies a given domain-event-listener rule from theset of domain-event-listener rules by determining that the entityidentifier satisfies a logic condition for a type of digital entity, adigital-entity-creation time, an object-event-occurrence time, or anobject-event type.
 14. The non-transitory computer-readable medium ofclaim 9, further comprising instructions that, when executed by the atleast one processor, cause the computing device to: provide, for displaywithin a graphical user interface of an administrator device, aselectable domain-event-listener condition in relation to the entityidentifier of the domain-event object; receive, from the administratordevice, an indication of a selection of the selectabledomain-event-listener condition; and based on the selection of theselectable domain-event-listener condition, add the selectabledomain-event-listener condition as a domain-event-listener rule to theset of domain-event-listener rules.
 15. The non-transitorycomputer-readable medium of claim 14, further comprising instructionsthat, when executed by the at least one processor, cause the computingdevice to: provide, for display within the graphical user interface ofthe administrator device, a platform-action option for the platformaction to be performed upon satisfaction of the domain-event-listenercondition; receive, from the administrator device, an indication of aselection of the platform-action option; and based on the selection ofthe platform-action option, associate the platform action with the setof domain-event-listener rules such that the platform action isperformed upon satisfying the domain-event-listener condition.
 16. Asystem comprising: at least one processor; and at least onenon-transitory computer-readable storage medium storing instructionsthat, when executed by the at least one processor, cause the system to:receive, within a multi-platform data stream, a set of domain-eventobjects comprising entity identifiers and object events; identify, fromthe set of domain-event objects, a domain-event object based on anentity identifier for the domain-event object satisfying a set ofdomain-event-listener rules for a digital-analytics platform; identifyan object event for the domain-event object; and based on the entityidentifier and the object event for the domain-event object, perform aplatform action within the digital-analytics platform.
 17. The system ofclaim 16, further comprising instructions that, when executed by the atleast one processor, cause the system to perform the platform action bytransmitting an electronic communication, configuring a ticket,triggering a platform process, modifying a platform workflow, updating adigital reporting interface, or modifying a platform parameter withinthe digital-analytics platform to reflect the identified domain-eventobject.
 18. The system of claim 16, further comprising instructionsthat, when executed by the at least one processor, cause the system todetermine that the entity identifier satisfies a givendomain-event-listener rule from the set of domain-event-listener rulesby determining that the entity identifier satisfies a logic conditionfor a type of digital entity, a digital-entity-creation time, anobject-event-occurrence time, or an object-event type.
 19. The system ofclaim 16, further comprising instructions that, when executed by the atleast one processor, cause the system to: generate a new domain-eventobject; generate a domain-event object schema for the new domain-eventobject comprising domain-event-listener conditions to identify the newdomain-event object within the multi-platform data stream; and providethe domain-event object schema to a schema library for themulti-platform data stream.
 20. The system of claim 16, furthercomprising instructions that, when executed by the at least oneprocessor, cause the system to identify an additional platform actioncorresponding to an additional platform taken in response to thedomain-event object.